Security Fix for Prototype Pollution - huntr.dev #252
Merged
+3
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@yoshino-s (https://huntr.dev/users/Yoshino-s) has fixed a potential Prototype Pollution vulnerability in your repository 🔨. For more information, visit our website (https://huntr.dev/) or click the bounty URL below...
Q | A
Version Affected | *
Bug Fix | YES
Original Pull Request | 418sec#1
If you are happy with this disclosure, we would love to get a CVE assigned to the vulnerability. Feel free to credit @yoshino-s, the discloser found in the bounty URL (below) and @huntr-helper.
User Comments:
📊 Metadata *
Bounty URL: https://www.huntr.dev/bounties/1-npm-expr-eval/
⚙️ Description *
With speficific input attckers can define properties on prototype, which will lead to prototype pollution.
💻 Technical Description *
when we access global value, it will just search by
item.value in expr.functions, with which we can also access toprototype,__proto__,constructor, and assign some properties on it.🐛 Proof of Concept (PoC) *
🔥 Proof of Fix (PoF) *